Node-RED block in Snap4City Microservice library node-red-contrib-snap4city-developer is "address-poi-search-by-text-near-gps-position">
    <p>it allows to retrieve a list of street addresses and service names based on a text search. The search may be filtered
        excluding POIs and to be within a maximum distance from a GPS position.</p>

    <h3>Inputs</h3>
    A JSON with these parameters:

    <dl class="message-properties">
        <dt>search
            <span class="property-type">string</span>
        </dt>
        <dd> the keywords separated with spaces that have to match with any textual description associated with an entity.</dd>
        <dt>latitude
            <span class="property-type">number</span>
        </dt>
        <dd> latitude of a GPS position</dd>
        <dt>longitude
            <span class="property-type">number</span>
        </dt>
        <dd> longitude of a GPS position</dd>
        <dt>maxdistance
            <span class="property-type">number</span>
        </dt>
        <dd> maximum distance from the GPS position of the services to be retrieved, expressed in Km (0.1 is used if parameter
            is missing) if it is equal to “inside” it searches for services with a WKT geometry that contains the specified
            GPS position (e.g a park)</dd>
        <dt>maxresults
            <span class="property-type">number</span>
        </dt>
        <dd> maximum number of results to be returned (if parameter is missing 100 is assumed), if it is 0 all results are returned</dd>
    </dl>

    <h3>Outputs</h3>
    <ol class="node-ports">
        <li>ServiceUri Array
            <dl class="message-properties">
                <dd> Returns an array containing the servicesUri of each service found</dd>
            </dl>
        </li>
        <li>GeoJSON Results
            <dl class="message-properties">
                <dd> A GeoJSON FeatureCollection object with the matching objects</dd>
            </dl>
        </li>
    </ol>

    <h3>Details</h3>
    <p>The node can receive a JSON with the parameters described in the Inputs section and with them generate the output JSON.
        If the values are not present in the input JSON, these are read by those in the configuration. If they are not present
        in either part, an error is generated for the necessary parameters.</p>